Conversation
This reverts commit 0a20d9f.
There was a problem hiding this comment.
Would we ever relay fiat shamir from the relayers given that it is 3x more expensive? I do not think we need any relayer changes here. Maybe a one shot command, that we could use in a playbook to unstuck the beefy client.
A more important relayer change is to make sure the beefy and on-demand-beefy relayer abandons a ticket if someone has successfully submitted a fiat shamir with a block greater than your tickets block.
This PR is mainly intended to address a specific use case where the end user is willing to bear the full cost of both the consensus update and the message execution for time-sensitive scenarios (as mentioned by the Hydration team in the channel). In such cases, the message relay will submit the Fiat-Shamir consensus update together with the message update.
Yes, we add a one shot command for submit Fiat-Shamir in this PR.
Yes, we've added this check, as mentioned in https://github.com/Snowfork/snowbridge/pull/1565/files#r2563477732 before |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1565 +/- ##
=======================================
Coverage 91.02% 91.02%
=======================================
Files 19 19
Lines 903 903
Branches 164 164
=======================================
Hits 822 822
Misses 64 64
Partials 17 17
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
yrong
changed the title
yrong
changed the title
yrong
changed the title
2 participants
Context
Introduces an
--instant-verificationflag for the parachain-v2 relayer, replacing the continuous streaming listener with a poll-and-deliver model.Instead of always-on BEEFY tracking in the light client, the relayer periodically scans for undelivered messages against the latest BEEFY block on the Relay chain, evaluates fee profitability, triggers an on-demand BEEFY sync (via Fiat-Shamir), and then submits the messages — all in one shot.
This is designed to reduce costs by only syncing BEEFY when there are profitable messages to deliver.